-
-
Notifications
You must be signed in to change notification settings - Fork 616
fix(openapi-fetch): omit serializing for already serialized data #2556
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
👷 Deploy request for openapi-ts pending review.Visit the deploys page to approve it
|
🦋 Changeset detectedLatest commit: d8424bb The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
drwpow
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, thank you!
|
Apologies, I am onboard with this change but the tests were actually failing. I had thought the CI failures were unrelated, caused by something else in CI was failing. But you actually introduced breaking behavior in your change. Please feel free to take another shot at it, off of latest |
Changes
New changes makes omitting serializing for already serialized data, such as string, primary fixing issue with sending
stringasbodyHow to Review
Take a look at the issue: #2555 and on updated code and test.
Checklist
docs/updated (if necessary)pnpm run update:examplesrun (only applicable for openapi-typescript)